We'll need a test to this

@Slike9 ping, what is the status of this PR? Can you add a test-case?

test fails (PostgresqlArrayTest#test_multi_dimensional)

Getting this error on v4.0.0.beta1 too

@Numerico on 4.0.0 too?

that's right. (or you mean to test it against 4.0.0 instead of 4.0.0.beta1?)

i finally by-passed it having an array of strings instead of integers, but I suppose it should work for ints, shouldn't it?

I can confirm this is a problem and the pull request fixes it, so I am unsure why this has been closed. Can someone @Slike9 or @rafaelfranca re-open the issue?

@hubertlepicki can you describe what problem you ran into. The PR description says it fixes the issue with t.integer :field_name, :type => :array . However that already works in master. Thanks.

Tell you what, I'll make a separate pull request as this is, indeed similar, but slight different issue than described at least in the description here.

This issue stops me from upgrading one of the apps to Rails 4. Fix in #11245 seems to resolve the issue. Just wanted to give heads up.

Also run into this issue in Rails 4.0.0. On a side note, type: :array did not work for me, I had to use array: true to get AR to even recognize the field as an array.

Changing the field to be of type string instead of integer also resolved the problem.

Closing this PR. We have #11245 with a working solution. @Slike9 thanks for your work 💛